[SOLVED] Corrupted Update (ieproxy.dll not applicable to this machine, no IE9/IE10)

H

howllerman

Contributor
Joined
Jul 2, 2013
Posts
9
Greetings!

I have been hunting this problem down for quite some time, and in a recent posting you did for Melerland7 (https://www.sysnative.com/forums/windows-update/6263-windows-7-update-error-800f0900.html) it looks like the closest thing to the same thing happening to me.

First things first:
  • Home built hot-rod with OEM Windows 7 64bit - no recovery disk. 3770K, MSI MB, Corsair H2O cooler, memory, and case, OC @ 4.6 (but with Turbo still enabled - idle is a nice low 3.5GHz).
  • No backup (Yes, I know - my bad, particularly with OEM version!)

Somewhere after May 15 2013 my Explorer windows stopped opening in the same window. I also received errors while running my flight simulator (MSFT FSX and Real Environment Extreme (REX)) about the Internet Explorer\ieproxy.dll either corrupt or not being correct for this platform.

Internet Exploder... err. Explorer stopped working altogether, and the update logs show conflicts for updates for IE9 (which exists) and IE10 (which I tried to correct the ieproxy.dll problem with). Funny thing: the May 15 update included a patch for IE10 - I did not have IE10 installed!!!

I have run scf /scannow and it generates a ton of messages, similar to those for Melerland7 above.
I have done the IF EXIST modification - nope.
I have done the KB947821 modification - nope.

What did work, to a certain degree, is the "windowsupdate.diagcab" - I don't know what it did, but it seems to be a brute-force little thing that fixed my Explorer window generation problem. It did say that it could not fix the IE9 update problem, and that I have "Cryptographic Services Components are not registered" problem.

IE9/IE10 still blow up/fail to initialize, and I cannot deinstall IE10 (the program removal tool fails) and cannot reinstall IE9 (get a 9C4D error). Attempts to reinstall IE10 yield a 9C48 error. Stuck in limbo...

I have Malwarebytes Pro, Spybot, and Avast Pro running, so I don't think it was a virus (never know, though, do we). I have a suspicion that my son may have interrupted some update process, although the logs don't say anything except that the update failed.

I will happily donate the registration cost of Malwarebytes Pro if you can get me back to a clean state (after which I will do a BACKUP!).

Thanks for the help!

Howellerman
 
Hello Howellerman, and welcome to Sysnative :)

Please copy and paste into your next reply between
Code:
tags the contents of C:\Windows\IE9_main.log and the contents of C:\Windows\IE10_main.log in a separate set of code tags (if they exist).

Finally,
Export CBS folder

  1. Click the Start button
    StartButton_16x16.gif
    then click Computer.
  2. Double-click on the C: drive, under the Hard Disk Drives category, and then scroll down to, and double click on the Windows folder.
  3. Find and double click on the Logs folder.
  4. Right-click on the CBS folder, and select Copy.
  5. Go back to your Desktop, right-click on it, and select Paste. You should now see a copy of the CBS folder appear on your Desktop called CBS.
  6. Right-click on this new folder, and navigate through Send to, and select Compressed (zipped) folder.
  7. A new file, also called CBS (CBS.zip), but this time with a different icon, will be created. Please upload it here.

Thank you!

Richard



These are just notes to myself - please ignore them. These instructions do not apply yet as you can't yet uninstall IE10/IE9. But...you have a versioning issues for which this is the fix once we manage to get it to uninstall.

Read More:
 
Hi Richard,

Thanks for getting back to me.

Attached are the IE9/IE10_main.log files, as well as the CBS.zip file you requested. There are a *ton* of entries in the CBS file, but I left them all there in case there is something in the history you can find.

Thanks!
 

Attachments

Hello again :)

Thanks a lot for those logs. It wasn't actually quite what I expected to see, but in a good way :)

Firstly, I would like to say that all of your IE9 & IE10 installation errors occured because a newer version of IE was already installed. And this is actually correct.

The krux lies here:
howllerman said:
Funny thing: the May 15 update included a patch for IE10 - I did not have IE10 installed!!!
Click to expand...

Looking over your logs, that wasn't an update you installed. It was a cumulative package containing the full base IE10 + several updates for it. So actually it does make more sense put like that :)

Now that you have IE10 installed, IE9 is guaranteed to fail with "newer version already installed". But the deal is, that package contained the base package + several updates. This is important: you are not on the base package. You are on a version slightly newer than the base package. But the IE10 package you downloaded from Microsoft *is* the base package. It's an older version than what you have. So it also fails with "newer version already installed" error code.


So...actually, things aren't as bad as they seem! First things first, do you mind being on IE10, provided I make it work properly & fix your other problems? I would recommend it personally, and if you are happy with that, we'll just leave it installed as actually it's in a reasonably healthy state at the moment. I'll then start targetting your other problems in other ways. First one first, ieproxy.dll issues. I'll have a go at fixing that, then we'll see what issues, if any, remain afterwards.

So, please open a Command Prompt: Open a Command Prompt window

Then type in "sfc /scannow" and press enter. The scan will take about 15 minutes. Once it has completed, please upload another set of CBS logs (they are indeed very long, but I'm used to skipping straight to the relevant sections :) )

Thank you!

Richard
 
Heya Richard,

Ah, so that explains the IE10 entry in the Update logs.

Fundamentally, I don't have a problem with keeping IE10 so lets keep it - hopefully it will simplify things as well.

I have attached the new CBS.zip file.

Thanks for the help, Richard!

John
 

Attachments

Last edited:
Awesome! Thanks for that! You're definitely right though...your IE installation is a bit (well, quite a lot, actually :p) in limbo between IE9 and IE10.

Regarding this...

howllerman said:
I have done the KB947821 modification - nope.
Click to expand...

What happened exactly? Did it install (takes up to an hour to complete) & not help, or did it fail to install with some error message?

If it failed to install with an error message: what was the message? (please re-run it to find out if you've forgotten)
If you cancelled it because it was taking too long: did you leave it at least an hour? If not, please re-run it and leave it at least an hour. If it did or does take more than an hour, please cancel it again and upload the logfile (path below)

Finally, whether or not it installed successfully, if the following file exists, please upload it: C:\Windows\Logs\CBS\CheckSUR.persist.log

Thank you!

Richard

P.S. SFC and the System Update Readiness Tool are designed to target differerent types of corruption (and if they didn't Microsoft wouldn't have created both). Looking at your SFC report I see that your corruptions really lie in the areas targetted by System Update Readiness Tool, so that is why I need to collect that logfile. I've already nailed down a pretty good idea of what's going on with this machine, and hopefully this logfile will give me the specifics I need to begin a fix.
 
Heya Richard,

KB947821 ran NOT. It said The update is not applicable to your computer.
Here are the things that I have run:
windowsupdate.diagcab - This was the most bang for the buck. It fixed a couple of things, most importantly that blasted "open in new window" error for Exploder.
MicrosoftFixit.Performance.LB.108295364690860899.10.1.Run
MicrosoftFixit.wu.RNP.108295364690860899.5.1.Run
MicrosoftFixit50778.msi
MicrosoftFixit50195.msi
IE9-Windows7-x64-enu.exe
EIE10_EN-US_WOL_Win764.EXE

I also have Process Explorer installed - a great little tool.

I have attached the CheckSUR.persist.log file.

Thanks for the help, Richard. This *would* have been so much easier if I took a backup, but my lab-rat days (I ran a performance/benchmark lab in my second career) got me in the "if it does not work, mind-wipe it!" mode. Makes for a lousy sysadmin, eh? :)

John
 

Attachments

Hello again John!

I don't care what incorrect return code the System Update Readiness Tool gave you....it created a logfile and it has given me the data I need :)

Let's go for everything in one big fix! I'll then do a complete re-assessment and see what's left.

WARNING: This fix has been created specifically for this user. If you are not this user, do not follow these instructions as you may cause serious harm to your computer.

Download a copy of SFCFixScript.zip attached to this post, and save it to your Desktop.
Then download a copy of SFCFix.exe from here: https://www.sysnative.com/forums/downloads/sfcfix/, and also save it to your Desktop.
Single click on SFCFixScript.zip and drag and drop it on top of SFCFix.exe. SFCFix will open and perform a fix for your corruptions.
A logfile called SFCFix.txt will open (and be saved to your Desktop). Please copy and paste the report into your next reply.


Then, please re-run the System Update Readiness Tool, and post another C:\Windows\Logs\CBS\CheckSUR.persist.log.


Next, re-run sfc /scannow.


Once complete, reboot your computer, give everything a try & let me know what's still broken. Finally, upload another copy of C:\Windows\Logs\CBS\CBS.log

Thank you!

Richard
 

Attachments

Thanks, Richard - I will give it a go when I get home from work today (slept in today - new puppy has put me sleep deprivation mode!).

Have a great night, and hopefully I will have some good news for you tomorrow!

John
 
No problem - happy to help, and very definitely in your own time :)

Enjoy the puppy :p
 
Heya Richard,

Close, so close... :)

Your SFCFixScript seemed to work, at least to my untrained eye.

KB947821 also worked - ran for quite some time, but said "update successful".

Unfortunately, the sfc /scannow still yields errors. I ran it before rebooting and again after rebooting. FYI: the reboot took a loooooonng time in the "starting windows" phase.

I have attached the requested files.

Based upon your SFCFixScript I am very optimistic!!!

Thanks, Richard!

John
 

Attachments

Thanks a lot for that John!

SFCFix has done a great job! 53 down, 4 to go - we may not be quite done yet, but I'm very pleased with our progress! :)

I'm currently at work & cannot put together the fix for you now, but I'll get to it asap.

Richard

P.S. Basically some of your other corruptions were masking these 4 & that is why I didn't include them in the first fix. Basically, SFC uses something called manifest files to detect whether other files were corrupt. You had 50 corrupt manifest files. Therefore there are a good couple of hundred files which SFC couldn't work out whether they were corrupt or not - and it turns out 4 of them were. I fixed all the manifest files in the last post (plus all 3 other corruptions SFC could detect), and then on your next run of SFC, it detected those next 4 files. Just a quick explanation of what's going on :)
 
Last edited:
Heya Richard,

Lo and behold, Windows Update fixed IE10 last night! Patch KD2859903 was applied via auto-update and IE10 runs.

Should I still run your newest patch?

John
 
howllerman said:
Heya Richard,

Lo and behold, Windows Update fixed IE10 last night! Patch KD2859903 was applied via auto-update and IE10 runs.

Should I still run your newest patch?

John
Click to expand...

Yes please, that script still applies :)

Richard
 
Genius!!!

I just installed your latest fix, ran sfc /scannow and it found corrupted files. However, it said a reboot would take of it.

Rebooted, and viola - sfc /scannow runs clean!!! :) Woo-hoo!!!

I promised to donate the cost of Malwarebytes Pro if you could fix this, $24.95.

Well, I am so appreciative, and impressed, that I am doubling down - still a LOT less expensive than what a Silicon Valley consultant would charge. eCheck for 50 USD posted to PayPal.

Thank you, Richard!

Now, on to perform that pesky backup! :)

John
 
Thank you so much John :)

Your donation is extremely gratefully received. Although we never expect donations, and it does not alter the quality of help given in any way, we are massively appreciative of any donation, no matter what size, as we are only a small forum, which does not run adverts, and the donations are what allows us to cover the running costs so that we can continue to help others free of charge in the future (and you never know, you might one day come back with another computer/another issue/whatever - but let's hope it's a curiosity question rather than a problem :) ). Thank you.

From my point of view, unless there are any lingering problems you would like help with, I'm done :) You are free to go and enjoy....Windows Update :r1:


Take care, it has been an absolute pleasure to work with you!

Richard
 
Heya Richard,

Same here - absolute pleasure, and as they say, you can stand down now... :thumbsup2:

I have referenced you to my Facebook page - *everyone* has to get bailed out now and then, no?

Is there a place to note the issue has been SOLVED, or do you take care of that?

John
 
howllerman said:
Heya Richard,

Same here - absolute pleasure, and as they say, you can stand down now... :thumbsup2:

I have referenced you to my Facebook page - *everyone* has to get bailed out now and then, no?

Is there a place to note the issue has been SOLVED, or do you take care of that?

John
Click to expand...

Thank you again :)

And yes, definitely :p Over the years, I've asked lots of questions myself actually (my particular weak point is hardware. And networking. And BSODs too sometimes. And I certainly can't do gaming. Actually, to be honest, I need help on almost anything non-Windows Update related! And I've even asked Tom about quite a few Windows Update threads I couldn't solve over the years. So yes, definitely!)

I've marked it as Solved now :) Technically, you have the power to do so, but I do not expect anyone to find it - it's usually something I handle (technically, at the top of the thread it's under Thread Tools, but as I say, you were not expected to find that for yourself :p)

See you around :)

Richard
 
You must log in or register to reply here.
Back
Top